System And Method For Providing A Synchronized Data Rerepresentation

ABSTRACT

A system and method for providing a synchronized data rerepresentation is provided. Data maintained by an originating application is accessed and the data is presented thorough an originating user interface. The data is marshaled into a form useable by a surrogate application with rerepresentation of the data through a surrogate user interface. Selections of the data are reflected across the originating user interface and the surrogate user interface. Actions on the data are synchronized between the originating application and the surrogate application.

FIELD

The invention relates in general to data rerepresentation and,specifically, to a system and method for providing synchronized datarerepresentation.

BACKGROUND

Productivity software continues to evolve to provide new applicationsthat exchange, process, manage, display, and represent data. However,despite the constant release of new or improved products, consumersoften simply desire a product that combines the merits of severalexisting applications to display or represent data in a way that isunsupported by any of the applications alone. Many Softwaremanufacturers attempt to accommodate customers by periodically offeringnewer versions or features of their applications, yet no singleapplication can capture the breadth of possible combinations ofdivergent applications into a single offering.

Data rerepresentation is a special presentation of data maintained by anexisting application, which is not ordinarily capable of providing thedesired special presentation. Lacking suitably customized applications,customers sometimes attempt to re-program existing applications toaccommodate their rerepresentaional needs, but often with only marginalsuccess. Existing solutions generally lack sufficient structuralstability. Innumerous functional interdependencies, legacy supportconsiderations, source tree limits, and countless other design andimplementational factors place constraints on the amount of change thatan application will safely tolerate without risk to runtime stability.Any change may perturb the entire system, which further increases thedifficulty of re-programming an existing application to flexiblyrerepresent data based on individualized need.

Application programming interfaces (APIs) offer only a partialalternative to re-programming data rerepresentation in an application.APIs facilitate data sharing between applications, which can becustomized as a rerepresentation. However, APIs are passive constructsparticular to each called application and require specific callbackfacilities from the receiving application to enable synchronization ofthe data with the sending application. Moreover, withoutsynchronization, a user is unable to switch back and forth between thedata representations of the applications, which can result ininconsistent data interpretation.

Conventional model-view-controller selections attempt to separate datafrom the user interface of an application to facilitate multiple viewsof the data. A controller processes user actions through the userinterface and updates a model, which maintains the data based on theuser actions. All views that depend on the model are also updated. Inaddition, the controller provides changes directly to the view, whichobtains data from the model. To change the view, though, the controllermust expressly reprogram the underlying application, which can undermineoperational stability and will also necessitate further modification ofthe application for each change in the view.

SUMMARY

Many users find themselves limited to organizational displays of dataprovided by an original application. Often, the user is unable togenerate “customized” displays of the data from the application alone.Application surrogacy provides the users with a rerepresentation of thedata through a surrogate application. The original application isaccessed, which displays the data in an original representation. Next,the surrogate application and associated data is accessed. The data fromthe original application is placed over the data of the surrogateapplication to create the rerepresentation. State and selectionconsistency of the data is respectively maintained between the originalapplication and associated data representation and the surrogateapplication and associated data rerepresentation. Logical consistencycan also be maintained.

An embodiment provides a system and method for maintaining dataconsistency. An original representation of data is obtained. The data isprovided as a representation. State and selection consistency of thedata is maintained between the original representation and thererepresentation.

A further embodiment provides a system and method for providing asynchronized data rerepresentation. Data maintained by an originatingapplication is accessed and the data is presented thorough anoriginating user interface. The data is marshalled into a form useableby a surrogate application with rerepresentation of the data through asurrogate user interface. Selections of the data are reflected acrossthe originating user interface and the surrogate user interface. Actionson the data are synchronized between the originating application and thesurrogate application.

Still other embodiments will become readily apparent to those skilled inthe art from the following detailed description, wherein are describedembodiments by way of illustrating the best mode contemplated. As willbe realized, other and different embodiments are possible and theirseveral details are capable of modifications in various obviousrespects, all without departing from the spirit and the scope.Accordingly, the drawings and detailed description are to be regarded asillustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram showing, by way of example, acomputer displaying multiple representations of data.

FIG. 2 is a functional block diagram showing, by way of example, adistributed system for rerepresenting data, in accordance with oneembodiment.

FIG. 3 is a functional block diagram showing logical components used inrerepresenting data, in accordance with one embodiment.

FIG. 4 is a functional block diagram showing, by way of example, astandalone system for rerepresenting data.

FIG. 5 is a timing diagram showing data collection and transmission by acollector and an emitter.

FIG. 6 is a process flow diagram showing a synchronization process for acollector.

FIG. 7 is a process flow diagram showing a synchronization process foran emitter.

FIG. 8 is a block diagram showing, by way of example, a distributedgraphical rerepresentation of data.

FIG. 9 is a block diagram showing, by way of example, a local textualrerepresentation of data.

DETAILED DESCRIPTION

New applications and new versions of existing applications arecontinually being introduced. Notwithstanding, users often desire“customized” applications that combine various data representationalaspects of individual applications not satisfactorily addressed by theapplications existing on the market. With rare exception, a user may beable to re-program an application to adjust the features; however, manyapplications are unable to satisfactorily accommodate change.

Rerepresentation System

Application surrogacy allows a user to rerepresent data from two or moreseparate applications while maintaining selection and consistency of thedata between the different representations. The approach leaves theunderlying applications unmodified and therefore stable.

In general, every application represents data visually, internally, andlogically in a manner consistent with the application's overall purposeand as dictated by the operational environment. FIG. 1 is a functionalblock diagram 1 showing, by way of example, a computer 2 displayingmultiple representations of data. A user can execute availableapplications through the user interface of the operating system. Forinstance, a personal information manager, such as Outlook, licensed byMicrosoft Corporation, Redmond, Wash., and a Web browser application,such as Internet Explorer, also licensed by Microsoft Corporation,supra, are two forms of productivity software frequently found in aworkplace. Personal information managers provide access to email,calendaring, tasks, contact information, and similar personalcommunications or organizational tasks. Web browsers facilitate viewingof Web content frequently downloaded from a network, including a publicdata communications network, such as the Internet.

The look and feel of an application is frequently influenced strongly bythe main purpose served. A personal information manager 3, includestabular listings 4 of individual data items 6 organized under columns orfields 5, in an original representation. Conversely, Web browsers,centrally feature a graphical window within which Web content includingtextual, visual, and audio content are presented. In large, a user'sviewing and use of the data is dictated by the data representationallimitations of each application. A user of a personal informationmanager 3 is forced to interpret his email 6, for instance, in terms ofthe available columns or fields 5. As a result, a user could notordinarily be able to organize his email 6 viewing by the locations ofthe sending correspondence.

A rerepresentation of the emails 6 can be generated using a surrogateapplication. First, the surrogate application, such as Yahoo! Maps,published as Web content by Yahoo! Inc., Sunnyvale, Calif., can beaccessed by the computer 2 through a Web browser. Next, the emails 6from the personal information manager 3 are placed over a map ofCalifornia 7 to create a rerepresentation, which provides a spatialdisplay of the emails 6, each represented by an icon 9 placed over alocation within the state of California map 7. The placement of theemails on the map provides a visualization of where the senders of theemail 6 are located.

Rerepresentations bring together two or more applications and theirdata. The applications and the data can be located external to thecomputer in a distributed system, such as described further below withreference to FIG. 2. Alternatively, the applications and the data can belocated on the same physical computer 2, such as further described belowwith reference to FIG. 4. Specific rerepresentation arrangements willnow be discussed.

The data 6 shared between the original representation and thererepresentation can be maintained using an application surrogate 8. Theapplication surrogate 8 applies an Emitter-Base-Collector model to theoriginal representation and the rerepresentation to synchronize data formaintaining state, selection, and logical consistency. Application ofthe Emitter-Base-Collector model is described further with reference toFIG. 3.

Distributed Rerepresentation

The Web has increasingly become a repository of arcane and wide ranginginformation, much of which may be useful in driving new forms ofrerepresentations. Most Web content is available online via remotesources. As well, historically standalone applications have beenincreasingly implemented online through standard Web interfaces. Thedistinctions between local and remote applications, as well as theirdata, has thus been blurred in favor of distributed arrangements.

Rerepresentation can occur in a distributed manner. FIG. 2 is afunctional block diagram showing, by way of example, a distributedsystem 10 for rerepresenting data, in accordance with one embodiment. Anend-user computer 11 is connected to a server 14 via an internetwork 16,such as the Internet. The server 14 can include, for instance, a Webserver 16 that is coupled to a database 17, which stores Web pages 18for perusal by end users. Other end-user devices, such as a desktop 11computer, a notebook computer 12, a handheld device, such as a PersonalDigital Assistant (PDA) 13, and a Web-enabled cellular telephone 15,could also be used for rerepresentation. At a minimum, each deviceshould include accessibility to an internetwork and have an ability toexecute an application. For clarity, rerepresentation will be discussedwith reference to only the computer 11, but applies generally to allsuch end-user devices 12, 13, 15.

The computer 11 accesses distributed Web-based applications 19, 21, 23for processing and displaying data. The data can include text, numbers,images, and sound bites. Other types of data are possible. Eachapplication 19, 21, 23 includes data stored in a remote database 20, 22,24. For example, a Web mail application 21 has an associated inboxdatabase 22, which contains user email. A Web contacts application 19has an associated contacts database 20. Similarly, a Web mapsapplication 23 has an associated maps database 24. The computer 11executes these applications and their data by accessing Web pages 18centrally served through the Web server 16 to access and display thedata stored in the databases 20, 22, 24.

Mashups are an increasingly popular approach to combining the datafunctionality, often online, of different Web-based applications. Amashup combines data from multiple sources to generate a single tool.The applications can communicate and share through published applicationprogramming interfaces (“API”) and can generate rerepresentations of theshared data. For example, Web mail inboxes generally include orderedlists of email, which can be sorted by field, such as sender, subject,date, time, and size. A user is generally unable to display the emailsby fields other than those provided. To rerepresent the email, the usercan apply a mashup to combine data from other sources, such as the Webmaps and Web contacts applications. Map data from the Web mapapplication is combined with contact data from the Web contacts to placethe email on a map location matching the sender's location. The mashupthus provides a rerepresentation of the emails in the Web mailapplication, which are each displayed by the location associated withthe sender in the contacts database.

Synchronicity and interactivity are respectively provided between theoriginal application and representation and the surrogate applicationand rerepresentation using an Emitter-Base-Collector model. FIG. 3 is afunctional block diagram showing logical components 30 used inrerepresenting data, in accordance with one embodiment. Through theEmitter-Base-Collector model, state, selection, and logic consistency ofthe data can be respectively maintained between the original applicationand associated data representation and the surrogate application andassociated data rerepresentation. Other processes for synchronizing dataare possible.

A collector 34 is associated with an original application and tracksprimary actions of a user applied to the user interface of the originalapplication, which displays or provides data to the user in an originalrepresentation 35. The collector 34 provides the primary actions to abase 31. In turn, the base 31 marshalls the primary actions to anemitter 32 that is associated with a surrogate application, whichapplies the primary actions to the user interface of the surrogateapplication, which displays or provides the same data as arerepresentation or a surrogate representation 33. As used herein, anyreference to a “rerepresentation” or “surrogate representation” will beunderstood to include the other term, except as specifically indicatedotherwise.

The collector 34 can also maintain ancillary data 36. Ancillary data 36is data or metadata that can be used to supplement the data forrerepresentation. For instance, rerepresenting textual data as spatialdata can require ancillary data 36 that includes locational information,such as spatial coordinates or an address. The ancillary data 36 can beextracted from the data itself or accessed from a separate applicationthat works congruently with the original representation through theoriginal application. The collector 34 also tracks updates to theancillary data 36 and provides the updates to the base 31. The base 31then provides the updates to the emitter 32 for applying to thesurrogate representation 33. Other forms, types, and sources ofancillary data are possible.

The emitter 32 collects surrogate actions performed by the user upon auser interface of the surrogate application. The emitter 32 transmitsthe surrogate actions to the base 31, which marshalls the surrogateactions and further transmits the surrogate actions to the collector 34for applying to the original application.

Standalone Rerepresentation

Standalone rerepresentation is a simplification of the more generalizeddistributed arrangement. In a standalone arrangement, the applicationsand data can be stored locally on the computer 11. FIG. 4 is afunctional block diagram showing, by way of example, a local system 40for rerepresenting data. The computer 11 accesses original applications41, 42 maintained locally for processing and displaying data, such as aword processing application 41 and a spreadsheet application 42. Eachapplication 41, 42 stores data specific to the format used by theprogram, specifically text documents 45 and spreadsheets 46,respectively. The data can be stored locally as files 43, 44 maintainedon the computer 11.

Each application, whether local or distributed, publishes an API throughwhich other applications can directly interact. The range of operationsavailable to a calling application via an API vary depending upon thecalled application. For purposes of rerepresentation, the calledapplication is referred to as the original application and the callingapplication is referred to as the surrogate application. The originalapplication's API must provide access to the data to be rerepresented,as well as the ability to remotely influence application behavior. Dataaccess and remote behavior control enable the Emitter-Base-Collectormodel to respectively provide state and selection consistency. In afurther embodiment, logical consistency, which reflects the completenessand consistency of data across the application is also provided, whereavailable through the original application's API.

Here, the spreadsheet application 42 embeds formulas and data cellinterdependencies directly into each spreadsheet 46. The word processingapplication 41 could become a surrogate application through theEmitter-Base-Collector model to rerepresent the spreadsheet data as atext document 45. The collector would obtain the spreadsheet data forthe base. The base would then marshall the spreadsheet data by, forinstance, interpreting each formula and understanding the datainterdependencies. The emitter would fully provide the marshalled datato the word processing application 41 for rerepresentation to the user.

Data Collection and Transmission

Data flow is moderated by the Emitter-Base-Collector model. FIG. 5 is atiming diagram showing data collection and transmission by a collector52 and an emitter 54. The axis 51 represents time. The collector 52 andemitter 54 both form connections 55, 56 to a base 53, which acts as ago-between. The Emitter-Base-Collector model is applied to both theoriginal representation of data and the rerepresentation of the samedata. An agent within the collector 52 watches the original applicationand records primary actions performed by the user through the userinterface. Similarly, an agent within the emitter 54 watches thesurrogate application and records surrogate actions performed by theuser through the user interface. The primary and surrogate actions caninclude selection of data or changes to the data, including adding,deleting, transferring, and altering the data. Other types of primaryand surrogate actions are possible.

The collector 52 collects and sends the primary actions (“PA1”) 57 tothe base 53. The base 53 receives the primary actions (“R-PA1”) 58 formarshalling and transmitting the marshaled primary actions (“T-PA1”) 59to the emitter 54. Once received, the emitter 54 applies the marshalledprimary actions (“D-PA1”) 60 to the rerepresentation of the data. Thesynchronization process is repeated for additional primary actions61-62.

In similar manner, the emitter 54 collects and sends the surrogateactions (“SA1”) 63 to the base 53. The base 53 receives the surrogateactions (“R-SA1”) 64 for marshalling and transmitting the marshaledsurrogate actions (“T-SA1”) 65 to the collector 52. Once received, thecollector 52 applies the marshalled surrogate actions (“D-SA1”) 66 tothe original representation of the data. The data synchronization isrepeated for additional surrogate actions 67-68.

The synchronization process of primary and surrogate actions, using theEmitter-Base-Collector model, provides state, selection, and logicalconsistency. State consistency ensures that changes due to events arereplicated in all representations. Selection consistency ensures that aselection made by a user is reflected in all of the representations.Logical consistency includes applying logic to ensure meaningfulconsistency and completeness of the data. Other consistencies arepossible.

To ensure that the consistencies are maintained, the actions can becollected and transmitted in real time, per a schedule, or upon demand.Other times for applying the Emitter-Base-Collector model are possible.In real time, the actions are collected and transmitted as they occur toprovide a user with the most up-to-date representations. A user can alsoschedule collection times for the actions performed on the originalinterface and the surrogate interface.

The action collections can be scheduled simultaneously at bothinterfaces or in sequence. The sequence can include a collection by thecollector and next, collection by the emitter, or vice versa. However,other patterns for sequenced collection are possible. The timing betweeneach collection can also be customized by the user, who can decide howoften the surrogate actions will be applied to the original interfaceand how often the primary actions will be applied to the surrogateinterface. For instance, if a user favors the surrogate representation,more actions will likely be performed on the surrogate interface thanthe original interface. The user can thus schedule the emitter tocollect and transfer actions more frequently than the collector.Further, the collector and emitter can submit a query to the base foractions. If available, the base then transmits any actions to therequesting module for application. Other processes and timing for datasynchronization are possible.

Operation Flow

The collector and the emitter perform similar sets of operations;however, the collector maintains the original representation and theemitter maintains the surrogate representation. FIG. 6 is a process flowdiagram showing a synchronization process 70 for a collector. Data isdisplayed through an original user interface by an original application.The collector collects primary actions performed upon the original userinterface (block 71). If the original application is communicating witha supplemental application, data provided by the supplementalapplication can be used as ancillary data. Updates to the ancillarydata, when available, are also collected by the collector (block 72).The primary actions and the ancillary updates, if applicable, areprovided to the collector by an agent that tracks the actions performedon the data in the original interface. The primary actions and theancillary data are then transmitted to the base for marshalling andfurther transmission (block 73). Meanwhile, the collector receivessurrogate actions collected by the emitter (block 75). The surrogateactions are received automatically or through requests from thecollector (block 74). Once received, the surrogate actions are appliedto the original representation (block 76). Other processes for thecollector, including other methods for receiving the actions, arepossible.

The emitter performs similar functions. FIG. 7 is a process flow diagramshowing a synchronization process 80 for an emitter. The emittercollects surrogate actions performed upon a surrogate interface (block81), which can result in changes to the data, as originally represented.The surrogate actions are then provided to a base for marshalling andtransmitting to a collector (block 82). Meanwhile, the emitter alsoreceives primary actions from the collector (block 84). The emitter cansubmit a query for the primary actions to the base (block 83);otherwise, the primary actions are received automatically. The emitterapplies the primary actions received to the surrogate representation tomaintain state, selection, and logical consistencies between theoriginal and the surrogate representations (block 85). Other processesfor synchronizing the data and receiving actions are possible.

Data Rerepresentation

Data representation is available in many different forms, includingmodification or projection formats, and graphical or textual formats. Inthe modification format, data is rerepresented by changing the form ofrepresentation, such as from graphical to textual or textual tographical representations. An example of a modification rerepresentationis discussed below with reference to FIG. 8. In the projection format,data displayed in a rerepresentation can include more or less data thanan original representation. State, selection, and logical consistenciesare maintained for the data shared between the two representations. Anexample of a projection rerepresentation is further discussed below withreference to FIG. 9. Other types of modification rerepresentations arepossible.

Graphical rerepresentation presents data using a graphical display, suchas a map, bar graph, chart, spatial representations, or a timeline. Anexample of a graphical rerepresentation is discussed below withreference to FIG. 8. Other types of graphical displays are possible.Textual rerepresentation involves representing data as text, which caninclude textual lists and text documents. An example of a textualrerepresentation is discussed below with reference to FIG. 9. Othertypes of textual displays are possible.

Graphical Rerepresentation

Email is a widely-used form of communication that allows users to shareinformation with others online. Email can also be used as a tool forcommunicating within an organization or across different organizations.Although email is offered by numerous ISPs and can be accessed throughdifferent applications, such as through an email client or a Webbrowser, the general set-up of an email inbox remains fairly standard.In general, each individual email is identified in an ordered list. Theorder can be determined using characteristics of the email, includingsubject, sender, time, date, and size, which are displayed as columns orfields. The spatial presentation and representation of the emails arelimited to the provided fields, which may not always provide an optionfor ordering or organizing data that is useful to a user. For example,imagine a manager of a world wide company who oversees sales groups inthe United States, Germany, and Japan. The members of the sales groupsare required to report to the manager at least once a week via email. Inaddition, the manager receives emails from customers across the world.To effectively respond to the large numbers of email received, themanager desires to graphically represent the email across a map of theglobe, which will aid him in interpreting the regional issues of concernto each sales group. The graphical representation allows the manager toattend to those emails that are sent from a particular location, such asBerlin, Germany, which is ten hours ahead of Seattle, Wash., beforethose of other areas where the work day has not yet begun. Othergroupings of data using a graphical rerepresentation are possible.

FIG. 8 is a block diagram showing, by way of example, a graphicalrerepresentation of data 90. An email inbox is commonly displayed as anordered list of emails 92 through an original user interface 91. Theordered list presents an original representation of the email. Eachemail is described by information fields, including sender 93, subject94, date 95, time 95, and size 96. A user can order the emails 92 inincreasing or decreasing order by selecting one of the fields 93-96. Theemails can also be sorted into folders created by the user. The sortingcan be based on the content of each email, such as email context, date,sender, and organization. Although the sorting and ordering of the inboxis helpful to organize large amounts of data, the user is unable torerepresent the data outside of the fields provided.

The user can access additional applications, such as a graphical displayto rerepresent the data. The data from the original representation canbe placed over a display of the additional application. The graphicaldisplay can include a map, bar graph, pie chart, and spatialdistributions, as well as other types of graphical representations.Returning to the above example, the international manager's emails areaccessed through a personal information management program. To create agraphical rerepresentation based on location, the emails are layeredover a map through a surrogate user interface. Together, the map and thedata form a surrogate representation 97. The surrogate representation 97allows the manager to visually determine a spatial distribution of theemails 92 received. The graphical rerepresentation 97 displays theemails by location, which can include, a home, work, or event location,as well as a location of the sender at the time that the email was sent.

Ancillary data can also be accessed by a collector to provide orsupplement the location information of each email. The ancillary datacan be obtained from a supplemental application that communicates withthe original user interface, from the data itself, or from informationassociated with the data. For instance, contact manager applicationsenable users to maintain a contact list, including information, such asname, location, position, telephone number, and contacts. The locationinformation can include a work address, home address, or satelliteoffice address. The location information for people that send emailsreceived in an email inbox can be obtained from the contact list asancillary data. If the ancillary location information is not available,the ancillary data can be obtained from the emails using the content ofeach email or information associated with each email, such as the emailaddress.

The location associated with each email can be used to place the emailson the map of the surrogate representation 97. The emails can bedisplayed, for instance, using an icon 98 located over the address,city, state, or country associated with the location. The icon 98 canrepresent an individual email or multiple emails over each location. Ifthe location of an email is undetermined, the email can be representedon the map by placing an undetermined icon 99 in a default city, state,or country having no other emails. The emails with undeterminedlocations can also be placed in an ocean or in a text box associatedwith the map. The undetermined icon 99 can be the same or different asthe icons that represent emails by location. Other icons and placementsof the emails are possible.

To assist the user in viewing map locations that contain many emails,the user can zoom in and out of selected locations using a cursor,remote control, buttons, or a toggle. Alternative arrangements of theemails can be applied at different zoom levels of the map. For example,on a world map, emails can be located by country. As the user zoomsfurther into one country, the emails can then be displayed by city and,when zoomed in further, the emails can be displayed by address.Additionally, distortions can be applied to the map to enlarge locationsthat contain more emails. Other map representations and characteristicsare possible.

Details about each email can be displayed by a popup box 100 when a userhovers over each icon with a cursor. The popup box can includeinformation, such as a number of emails represented, brief summaries ofthe content, attachments, a photograph of the sender, a different map,fields 93-96 from the original interface, further icons representing anurgent message, an important sender, and related emails. Other detailedinformation and displays of the information are possible.

The appearance of the icon can be adapted to reflect emailcharacteristics through icon actions. The icon actions can include thedisplay, shape, form, size, and movement associated with each icon. Forinstance, a location containing new email can include a mailbox with araised flag to indicate to the user that there is new mail.Additionally, if an email is urgent, the associated icon can flash,spin, or be colored red to catch the user's attention. The user cancreate the icons and icon actions used to display the emailcharacteristics or the icons and the associated actions can bepredetermined. Other types of icons and icon actions are possible.

When the original email inbox representation is displayed, the user canperform actions on the original interface to effect changes to theemails, including creating, deleting, selecting, editing, sending, orsaving an email message. An agent tracks and records the actions to theoriginal interface, which is collected by a collector. Returning to ourexample above, the international manager is reviewing all emailsassociated with New York, N.Y. After reviewing the first email, themanager decides to respond by sending an email. The first email is thenmoved to a folder titled “New York Office.” The second email is deleted,and the third email is opened, read, and kept in the email inbox. Theagent records the actions taken by the manager, which are collected bythe collector and transmitted to a base. The base then transfers theactions to an emitter. The emitter applies the actions to the surrogatemap representation. On the surrogate map representation, the content ofthe response message is created and stored in a sent folder, the firstemail is transferred from the email inbox to the folder titled “New YorkOffice,” the second email is deleted, and the third email remains in theemail inbox. If the third email is associated with an icon thatrepresents a status of the email, including an opened or unopenedstatus, the icon will be changed to represent the opening of the email.

The collector can also collect the updates to the ancillary data, whichare transferred to the base and then to the emitter. The emitter appliesthe updates to the surrogate representation. Similarly, actionsperformed on the surrogate interface are tracked, collected, andtransmitted for display through the original representation.

In one embodiment, the email can be spatially arranged on the surrogaterepresentation by categories, such as organization, business activities,and email content. Other spatial representations and categories ofrepresentations are possible.

Textual Rerepresentation

Textual rerepresentations allow a user to rerepresent data using text,such as text documents, text lists, and other forms of textual display.More specifically, a user can rerepresent data as a list of parts,redacted text, and reorganized text, as well via other displays of thedata. FIG. 9 is a block diagram showing, by way of example, a localtextual rerepresentation of data. An original representation 111 isdisplayed through an original user interface. In a further example, auser is preparing a patent application. Patent drawings accompany thetextual patent application and include reference numbers of parts orprocesses, which are further described in the application. The patentdrawings are prepared using drafting software, which provides theoriginal representation of data 111, including a drawing title 114 and asubject of the drawings, such as a car 112. The parts of the car arelabeled with reference numbers 113 to specifically identify eachparticular part in the drawings. The reference numbers are also used inthe patent application, which describes the car 112 and the car parts113 in detail.

Users often experience difficulty in keeping track of the referencenumbers used, as well as to what part each number refers. The referencenumbers can be rerepresented as a list of parts, which is a surrogaterepresentation of the data. Using the Emitter-Base-Collector model, theoriginal representation and the surrogate representation are processedto maintain state, selection, and logical consistency. An agent watchesthe original representation 111 and records primary actions performed onthe original interface, which can result in a change of the referencenumbers 113. The primary actions are collected by a collector fortransmission to a base, which marshalls the data and further transmitsthe primary actions to an emitter. The emitter applies the primaryactions to the surrogate representation 115, which displays the list ofparts.

Conversely, surrogate actions performed on the surrogate interface aretracked by an agent and transmitted to a base via the emitter. The basefurther transmits the surrogate actions to the collector, which are thenapplied to the original representation to maintain consistency betweenthe two different representations.

The synchronization provided by the Emitter-Base-Collector model can beapplied during the drafting of the drawings or after the drawings havebeen completed. When the model is applied during the drafting, referencenumbers will be added to the list after the user enters a new referencenumber in the drafting software. Other actions, such as the replacement,deletion, and change of order of the numbers will also occur in parallelto the drafting. Other timing or applications of theEmitter-Base-Collector model are possible.

While the invention has been particularly shown and described asreferenced to the embodiments thereof, those skilled in the art willunderstand that the foregoing and other changes in form and detail maybe made therein without departing from the spirit and scope of theinvention.

1. A system for maintaining data consistency, comprising: arepresentation module to obtain an original representation of data; arerepresentation module to provide the data as a rerepresentation; and abase to maintain state and selection consistency of the data between theoriginal representation and the rerepresentation.
 2. A system accordingto claim 1, further comprising: a logical consistency module to maintainlogical consistency of the data between the original representation andthe rerepresentation.
 3. A system according to claim 2, wherein thelogical consistency maintains completeness of the data between theoriginal representation and the rerepresentation.
 4. A system accordingto claim 1, wherein the state consistency maintains changes between therepresentation and the rerepresentation, comprising: a state consistencymodule to replicate the changes in the representation and thererepresentation.
 5. A system according to claim 1, wherein theselection consistency maintains selections by a user between therepresentation and the rerepresentation, comprising: a selectionconsistency module to reflect the selections in the representation andthe rerepresentation.
 6. A method for maintaining data consistency,comprising: obtaining an original representation of data; providing thedata as a rerepresentation; and maintaining state and selectionconsistency of the data between the original representation and thererepresentation.
 7. A method according to claim 6, further comprising:maintaining logical consistency of the data between the originalrepresentation and the rerepresentation.
 8. A method according to claim7, wherein the logical consistency maintains completeness of the databetween the original representation and the rerepresentation.
 9. Amethod according to claim 6, wherein the state consistency maintainschanges between the representation and the rerepresentation, comprising:replicating the changes in the representation and the rerepresentation.10. A method according to claim 6, wherein the selection consistencymaintains selections by a user between the representation and thererepresentation, comprising: reflecting the selections in therepresentation and the rerepresentation.
 11. A system for providing asynchronized data rerepresentation, comprising: a data access module toaccess data maintained by an originating application with presentationof the data through an originating user interface; a data marshall tomarshall the data into a form useable by a surrogate application withrerepresentation of the data through a surrogate user interface; and abase to reflect selections of the data across the originating userinterface and the surrogate user interface and to synchronize actions onthe data between the originating application and the surrogateapplication.
 12. A system according to claim 11, further comprising: anancillary data module to collect ancillary data maintained by anancillary application and comprising metadata; a metadata module tomatch the data to the metadata; and a data supplement module tosupplement the rerepresentation of the data with the ancillary datamatched by the metadata.
 13. A system according to claim 11, wherein thererepresentation comprises one of a graphical rerepresentation and atextual rerepresentation.
 14. A system according to claim 13, whereinthe graphical rerepresentation comprises one or more of a map, graph,pie chart, timeline, bar graph, and spatial distribution chart.
 15. Asystem according to claim 13, wherein the textual rerepresentationcomprises one or more of an ordered list and redacted text.
 16. A systemaccording to claim 11, further comprising: a structure module tostructure the rerepresentation by arranging the data through one or moreof location, temporal, and event characteristics.
 17. A system accordingto claim 11, further comprising: a processor to generate thererepresentation, comprising: an originating application module toaccess the originating application, which maintains the data, through aWeb based network; a surrogate application module to access thesurrogate application associated with surrogate data through the Webbased network; and a data combination module to combine the data withthe surrogate data to provide the rerepresentation.
 18. A method forproviding a synchronized data rerepresentation, comprising: accessingdata maintained by an originating application with presentation of thedata through an originating user interface; marshalling the data into aform useable by a surrogate application with rerepresentation of thedata through a surrogate user interface; reflecting selections of thedata across the originating user interface and the surrogate userinterface; and synchronizing actions on the data between the originatingapplication and the surrogate application.
 19. A method according toclaim 18, further comprising: collecting ancillary data maintained by anancillary application and comprising metadata; matching the data to themetadata; and supplementing the rerepresentation of the data with theancillary data matched by the metadata.
 20. A method according to claim18, wherein the rerepresentation comprises one of a graphicalrerepresentation and a textual rerepresentation.
 21. A method accordingto claim 20, wherein the graphical rerepresentation comprises one ormore of a map, graph, pie chart, timeline, bar graph, and spatialdistribution chart.
 22. A method according to claim 20, wherein thetextual rerepresentation comprises one or more of an ordered list andredacted text.
 23. A method according to claim 18, further comprising:structuring the rerepresentation by arranging the data through one ormore of location, temporal, and event characteristics.
 24. A methodaccording to claim 18, further comprising: generating thererepresentation, comprising: accessing the originating application,which maintains the data, through a Web based network; accessing thesurrogate application associated with surrogate data through the Webbased network; and combining the data with the surrogate data to providethe rerepresentation.